|
Event Viewer, a component of Microsoft's Windows NT line of operating systems, lets administrators and users view the event logs on a local or remote machine. In Windows Vista, Microsoft overhauled the event system.〔(New tools for Event Management in Windows Vista ) 〕 Due to the event viewer's reporting of processing errors. All critical errors requiring immediate technical support. == Overview == Windows NT has featured event logs since its release in 1993. Applications and operating-system components can use this centralized log service to report events that have taken place, such as a failure to start a component or to complete an action. The Event Viewer uses event IDs to define the uniquely identifiable events that a Windows computer can encounter. For example, when a user's authentication fails, the system may generate Event ID 672. Windows NT 4.0 added support for defining "event sources" (i.e. the application which created the event) and performing backups of logs. Windows 2000 added the capability for applications to create their own log sources in addition to the three system-defined "System", "Application", and "Security" log-files. Windows 2000 also replaced NT4's Event Viewer with a Microsoft Management Console (MMC) snap-in. Windows Server 2003 added the AuthzInstallSecurityEventSource() API calls so that applications could register with the security-event logs, and write security-audit entries.〔(【引用サイトリンク】 AuthzInstallSecurityEventSource Function ) 〕 Versions of Windows based on the Windows NT 6.0 kernel (Windows Vista and Windows Server 2008) no longer have a 300-megabyte limit to their total size. Prior to NT 6.0, the system opened on-disk files as memory-mapped files in kernel memory space, which used the same memory pools as other kernel components. Event Viewer log-files with filename extension evtx typically appear in a directory such as C:\Windows\System32\winevt\Logs\抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Event Viewer」の詳細全文を読む スポンサード リンク
|